• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    A spark ignition engine system for communicating data includes a capacitive discharge ignition system using a microcontroller for controlling the spark ignition of a light-duty internal combustion engine; a memory device communicated with the microcontroller, wherein the microcontroller obtains engine data from the light-duty internal combustion engine and stores the engine data or software using the memory device; and a powering connection and a separate data connection that are electrically connected to different pins of the microcontroller, wherein the powering connection supplies power to the microcontroller while engine data or software is communicated via the data connection.
    公开号:SE1551272A1
    申请号:SE1551272
    申请日:2014-03-12
    公开日:2015-10-05
    发明作者:Martin N Andersson；Cyrus M Healy；Russell R Speirs
    申请人:Walbro Engine Management Llc；
    IPC主号:
    专利说明:

    2630.3305.003 [1087] IGNITION DIAGNOSTICS SYSTEM Reference to Co-Pending ApplicationThis application claims the benefit of U.S. Provisional Application No.61/790,419 f1led March 15, 2013, Which is incorporated herein by reference in its entirety.
    Technical FieldThe present disclosure relates generally to internal combustion engines and more particularly to light-duty engine diagnostic systems.
    Background Various electronic ignition timing control systems for light-duty engines thatpower a Wide range of devices, such as laWn equipment, chainsaws, and the like areknown in the art. Typically, these ignition systems do not have any battery and theseengines are manually started With a pull-rope recoil starter. There is a need to obtaindata on the operation of these engines for diagnostic purposes and to program electronic control systems of these engines.
    SummaryAccording to one aspect of the disclosure, a spark ignition engine system for communicating data includes a capacitive discharge ignition system using amicrocontroller for controlling the spark ignition of a light-duty intemal combustionengine; a memory device communicated With the microcontroller, Wherein the microcontroller obtains engine data from the light-duty intemal combustion engine and stores the engine data or software using the memory device; and a poweringconnection and a separate data connection that are electrically connected to differentpins of the microcontroller, wherein the powering connection supplies power to themicrocontroller while engine data or software is communicated via the dataconnection.
    According to another aspect of the disclosure, a spark ignition engine systemfor communicating data includes a capacitive discharge ignition system using amicrocontroller for controlling the ignition of a light-duty intemal combustion engine;a memory device communicated with the microcontroller, wherein themicrocontroller obtains engine data from the light-duty intemal combustion engineand stores the engine data or software using the memory device; a data connectioncoupled with the microcontroller; a separate powering connection coupled with themicrocontroller for powering the microcontroller while engine data or software iscommunicated via the data connection; and an intermediary computing device that isdetachably coupled to the data connection and the powering connection while enginedata or software is communicated via the data connection.
    According to yet another aspect of the disclosure, a spark ignition enginesystem for communicating data includes a capacitive discharge ignition system usinga microcontroller for controlling the ignition of a light-duty intemal combustionengine; a memory device communicated with the microcontroller, wherein themicrocontroller obtains engine data from the light-duty intemal combustion engineand stores the engine data or software using the memory device; and a kill switch thatis removably-carried by a cover of the light-duty intemal combustion engine, wherein the kill switch is in communication with a data connection electrically linked to the microcontroller and with a separate powering connection electrically linked to the microcontroller, and when the kill switch is removed and disconnected from the dataconnection and the powering connection, an interrnediary computing device isconnected to the data connection for communicating data with the microcontroller and the powering connection for providing power.
    Brief Description of the Drawings The following detailed description of exemplary embodiments of thisdiagnostic system and test mode will be set forth with reference to the accompanyingdrawings in which: FIG. l shows a capacitor discharge ignition (CDI) system generally having astator assembly mounted adj acent a rotating flywheel; FIG. 2 is a schematic diagram of an embodiment of a control circuit that canbe used with the CDI system of FIG. 1; FIG. 3 is a block diagram of an embodiment of an interrnediary computingdevice used to access engine operating data; FIG. 4 is a block diagram of an engine, an interrnediary computing device, andan extemal personal computer (PC); and FIG. 5 is a flow chart of an embodiment of a method that can be used to record engine operating data.
    Detailed Description of Preferred Embodiments The methods and systems described herein generally relate to a light-dutygasoline powered spark plug ignited intemal combustion engine that includes microcontroller circuitry, which can record and store engine operating data. The stored data can be communicated to an external digital computer such as a personalcomputer (PC) through an interrnediary computing device. The interrnediarycomputing device may also perrnit the computer to be used to re-program or re-flashthe memory of the microcontroller. The engine preferably has a so-called kill switchmounted on a cowl, cover, or housing of the engine that is accessible from the exteriorof the engine housing and may be manually actuated by an operator to stop orterrninate operation of the running engine. Desirably, the kill switch can be removedfrom the engine housing and disconnected from terrninals at least some of which canthen be connected to the interrnediary computing device to supply electrical energy topower up the microcontroller and communicate data from the microcontroller to theextemal computer or from the computer to the microcontroller for re-programming orre-flashing the memory of the microcontroller. After the data communication iscompleted, the interrnediary computing device may be unplugged or disconnectedfrom the terrninals and the kill switch reconnected to them and attached to the housingfor continued use in stopping or terrninating operation of the running engine.Typically the light duty engine is a single cylinder two-cycle or four-cyclegasoline powered intemal combustion engine. A single piston is slidably received forreciprocation in the cylinder and connected by a tie rod to a crank shaft attached to afly wheel and typically having a capacitive discharge ignition “CDI” system forsupplying a high voltage ignition pulse to a spark plug for igniting an air-fuel mixturein the engine combustion chamber. These engines do not have a separate battery forsupplying an electric current to the spark plug and powering the engine electronic ignition control circuitry and micro-processer. Typically these engines are manually cranked for starting with an automatic recoil rope starter.
    The terrn "light-duty combustion engine" broadly includes all types of non-automotive combustion engines, including two- and four-stroke engines typically usedto power various devices, such as intemal-combustion gasoline-powered hand-heldpower tools, lawn and garden equipment, lawnmowers, weed trimmers, edgers, chainsaws, snowblowers, personal watercraft, boats, snowmobiles, motorcycles, all-terrain-vehicles, etc. The system and method can record data relating to one or moreoperating characteristics of a light-duty engine. This data can be obtained usingfirrnware stored on a microcontroller that also controls the engine system. That way,if a light-duty engine is retumed to the manufacturer (or other facility, such as a repairshop) after it was sold to its end user, technicians can access the data and try todetermine how the engine has been used or what, if anything, went wrong. In oneimplementation, the data can be obtained from the light-duty engine via a kill switchterminal that includes a powering connection and a data connection that are incommunication with the microcontroller of the device and communicated to anexternal computer.
    This system and method can aid the manufacturer with diagnosing problem(s)that may exist with respect to the engine. For instance, retailers can sell deviceshaving light-duty engines to consumers and often include a warranty that may beserviced by a manufacturer of the device. When a customer retums a device to theretailer, the underlying reason for the retum may not always be apparent to themanufacturer of the device. For instance, the manufacturer may initially inspect theengine of the device and find no defect. And it may be possible that a customer mayhave wrongly deterrnined that the engine does not operate correctly or simply not been entirely forthcoming about the actual use of the device. Therefore, when a technician later operates the retumed device it may appear to operate norrnally or in amanner inconsistent With the description offered by the customer/operator.
    In another example, light-duty engines may be used With devices incommercial settings and fail at the end of their service life. Determining the failurepoint of the light-duty engines used thusly can be valuable to determine service life oflight-duty engines and/or yield data that can be used to improve the design and servicelife of such engines in the fiJture. A thorough unit-by-unit investigation of possibleengine failures may be time consuming and unreasonable given the volume of devicesthat are manufactured. The engine data can reflect the performance of the engineand/or device When it Was used in its operating environment. It can then be accessedby a manufacturer or repair facility.
    As Will be explained in greater detail, light-duty engines can use a capacitivedischarge ignition (CDI) system 10-an example of Which is shown in FIG. l-thatincludes one of a number of control circuits, including the exemplary embodimentdescribed in relation to FIG. 2. The CDI system 10 generally includes a flyWheel 12rotatably mounted on an engine crankshaft 13, a stator assembly 14 mounted adjacentthe flyWheel, and a control circuit (not shown in FIG. 1). FlyWheel 12 rotates With theengine crankshaft 13 and generally includes a permanent magnetic element havingpole shoes 16, 18, and a permanent magnet 17, such that it induces a magnetic flux inthe nearby stator assembly 14 as the magnets pass thereby.
    Stator assembly 14 may be separated from the rotating flyWheel 12 by ameasured air gap (e. g. the air gap may be 0.3mm), and may include a lamination stack24 having first and second legs 26, 28, a charge coil Winding 30 and an ignition coilcomprising a primary Winding 32 and a secondary ignition Winding 34. The lamination stack 24 may be a generally U-shaped ferrous arrnature made from a stack of iron plates, and may be mounted to a housing (not shown) located on the engine.Preferably, the charge winding 30 and primary and secondary ignition windings 32,34 are all wrapped around a single leg of the lamination stack 24. Such anarrangement may result in a cost savings due to the use of a common ground and asingle spool or bobbin for all of the windings. The ignition coil may be a step-uptransforrner having both the primary and secondary ignition windings 32, 34 woundaround the second leg 28 of the lamination stack 24. Primary ignition winding 32 iscoupled to the control circuit, as will be explained, and the secondary ignitionwinding 34 is coupled to a spark plug 42 (shown in FIG. 2) of the engine. As isappreciated by those skilled in the art, primary ignition winding 32 may havecomparatively few tums of relatively heavy wire, while secondary ignition winding34 may have many tums of relatively fine wire. The ratio of tums between theprimary and secondary ignition windings 32, 34 generates a high voltage potential inthe secondary winding 34 that is used to fire spark plug 42 or provide an electric arcand consequently ignite an air/ fuel mixture in the engine combustion chamber.
    The control circuit is coupled to stator assembly l4 and spark plug 42 andgenerally controls the energy that is induced, stored and discharged by the CDIsystem l0. The term “coupled” broadly encompasses all ways in which two or moreelectrical components, devices, circuits, etc. can be in electrical communication withone another; this includes but is certainly not limited to, a direct electrical connectionand a connection via an interrnediate component, device, circuit, etc. The controlcircuit can be provided according to one of a number of embodiments, including theexemplary embodiment shown in FIG. 2.
    Referring now to FIG. 2, the CDI system l0 includes circuit 40 as an example of the type of control circuit that may be used to implement the ignition timing systems described herein. However, many variations of this circuit may altemativelybe used without departing from the scope of the invention. Circuit 40 interacts withcharge winding 30, primary ignition winding 32, and a kill switch terminal 44, andgenerally comprises a microcontroller 46, an ignition discharge capacitor 48, and anignition switch 50. The majority of the energy induced in charge winding 30 isdumped onto ignition discharge capacitor 48, which stores the induced energy untilthe microcontroller 46 perrnits it to discharge. According to an embodiment shownhere, a positive terminal of charge coil 30 is coupled to a diode 52 and a diode 59,which in tum is coupled to ignition discharge capacitor 48. A resistor 54 may becoupled in parallel to the charge ignition discharge capacitor 48.
    During operation, rotation of flywheel 12 causes the magnetic elements, suchas pole shoes 16, 18, to induce voltages in various coils arranged around thelamination stack 24. One of those coils is charge winding 30, which charges ignitiondischarge capacitor 48 through diode 59. A trigger signal from the microcontroller 46activates switch 50 so that the ignition discharge capacitor 48 can discharge andthereby create a corresponding ignition pulse in the ignition coil. In one example, theignition switch 50 can be a thyristor, such as a silicon controller rectif1er (SCR).When the ignition switch 50 is tumed “on° (in this case, becomes conductive), theswitch 50 provides a discharge path for the energy stored on ignition dischargecapacitor 48. This rapid discharge of the ignition discharge capacitor 48 causes asurge in current through the primary ignition winding 32 of the ignition coil, which intum creates a fast-rising electro-magnetic field in the ignition coil. The fast-risingelectro-magnetic field induces a high voltage ignition pulse in secondary ignition winding 34. The high-voltage ignition pulse travels to spark plug 42 which, assuming it has the requisite Voltage, provides a combustion-initiating spark. Other sparkingtechniques, including flyback techniques, may be used instead.
    The microcontroller 46, as shown in FIG. 2, can store code for the ignitiontiming systems described herein. In addition, the microcontroller 46 can also storecode for implementing the system and method described herein and/or storing theengine data obtained by the method. Various microcontrollers or microprocessorsmay be used, as is known to those skilled in the art. Examples of howmicrocontrollers can be implemented with ignition timing systems can be found inU.S. Patent No. 7,546,836 and U.S. Patent No. 7,448,358 which are incorporated byreference.
    For instance, the microcontroller 46 may include a reprogrammable EEPROMthat uses flash memory. The microcontroller 46 shown in FIG. 2 includes 8 pins. Pin8 of the microcontroller 46 can be coupled through a diode 74 to a Voltage sourcewhich supplies the microcontroller 46 with power. This will be discussed below inmore detail. The circuit 40 depicts capacitors 76 and 78, a zener diode 80, and aresistor 82 electrically connected in circuit to pin 8 as well. In this example, pin l is areset pin that is coupled to the Voltage source via a diode 64. Pin 2 is coupled to thegate of ignition switch 50 Via resistor 56, which is wired in circuit with zener diode6l, and transmits from the microcontroller 46 an ignition signal which controls thestate of the switch 50. When the ignition signal on pin 2 is low, the ignition switch 50is nonconductive and capacitor 48 is allowed to charge. When the ignition signal ishigh, the ignition switch 50 is conductive and ignition discharge capacitor 48discharges through primary ignition winding 32, thus causing a high-Voltage ignitionpulse to be induced in secondary ignition winding 34 and sent to the spark plug 42.
    Thus, the microcontroller 46 can goVem the discharge of capacitor 48 by controlling the conductive state of the switch 50. Pin 6 is coupled to the charge winding 30 viaresistors 84 and 86, zener diodes 88 and 90, and capacitor 92. Pin 6 receives anelectronic signal representative of the position of an engine piston in its combustionchamber usually relatiVe to the top dead center (TDC) location of the piston. Thissignal can be referred to as a timing signal. The microcontroller 46 can use the timingsignal to deterrnine engine speed, the timing of an ignition pulse relatiVe to thepiston(s), TDC position (usually from a look-up table), and whether or not and, if so,when to actiVate an ignition pulse. Pin 3 handles data communication input/outputand kill sensing. The piston position signal can also be referred to as a positive pulse.Pin 3 is coupled to the kill switch terrninal 44 Via resistors 58 and 60 and, capacitor62.
    Kill switch terrninal 44 acts as a manual oVerride for shutting down the engine.The kill switch terrninal 44 can include a powering connection 53 and a dataconnection 55 that each electrically communicate with the microcontroller 46 and areaccessible for sending/receiving data to/from the microcontroller 46. As used herein,the kill switch terrninal 44 may be used to collectively refer to a number of elementsthat are included within the dashed line shown on FIG. 2. The term “electricallycommunicates” can mean the communication of data and/or electrical signals (e.g.Voltage or current). The powering connection 53 can be electrically connected to pin8 of the microprocessor 46 via a diode 74 and a resistor 72. And the data connection55 can be electrically connected to pin 3 of the microprocessor 46 Via resistor 58. Pin4 acts as a ground reference for the microcontroller 46 and can be electricallygrounded as is known in the art. The ground reference (in this case Pin 4) can also beconnected to a ground terrninal lead 47, which electrically communicates with the microcontroller 46. While the powering connection 53, the data connection 55, and the ground terminal lead 47 are shown in FIG. 2 as being isolated from each other,these elements may be included separately in a single physical connector capable ofultimately communicating with a computing device, such as an extemal personalcomputer (not shown). In one example, the powering connection 53, the dataconnection 55, and the ground terminal lead 47 can be grouped together as part of thekill switch terminal 44. The powering connection 53 and the data connection 55 ofthe kill switch terminal 44 can be coupled to an interrnediary computing device thatwill communicate with a computer, such as the extemal PC, via a variety ofconnections that include universal serial bus (USB) ports or other parallel or serialports that are known. This will be discussed in more detail below.
    In one implementation, the kill switch terminal 44 can include a kill switchhaving a first fianction (to perrnit the stoppage of engine operation during normal use)and a second fianction (to perrnit the acquisition of data from the microcontroller 46).For example, the kill switch can be a momentary switch that is biased in the openposition perrnitting a user to engage the switch and stop engine operation. Here, thekill switch can be electrically coupled to the powering connection 53, the dataconnection 55, and the ground terminal lead 47. It is also possible that the kill switchincludes a plurality of positions, such as “OFF” and “ON.” In this case, each of theplurality of positions can be selected using a rotating member, such as a key. Whilecertain embodiments are described wherein data acquisition is accomplished by wayof a kill switch, any other switch or terminal coupled to the microcontroller 46 may beused. In this way, an existing switch or terminal may become a kill switch or terminalin that the existing component may have a first fi1nction during normal use of theengine and a second fi1nction to perrnit data acquisition from the microcontroller 46.
    Additionally, a switch or terminal communicating with the microcontroller 46 may be ll provided, and such a switch or terminal may perrnit data acquisition to and/or fromthe controller as its only purpose. That is, the switch or terminal might not have anyother use with regard to normal operation or shutting down of the engine.
    Each of the first fianction of engine use and the second fianction of engine usecan use a different electrical and/or physical configuration of kill switch terminal 44.For example, the kill switch terminal 44 can include the powering connection 53, thedata connection 55, and the ground terminal lead 47. The powering connection 53and the data connection 55 can each be attached to a blade-shaped terminal. This canbe appreciated from FIG. 2, which depicts the blade-shaped terminal for the poweringconnection 53 as power connection blade 53a and the blade-shaped terminal for thedata connection 55 as data connection blade 55a.
    In some implementations, the circuit 40 can be imprinted on a printed circuitboard (PCB) (not shown). And the powering connection blade 53a and the dataconnection blade 55a can be initially formed using a solid and/or unitary one-piecestructure such that blades 53a and 55a are connected to each other electrically andphysically. Both the powering connection blade 53a and the data connection blade55a can be electrically and/or physically attached (via solder, etc.) as a unitarystructure (e. g., a single piece) to the powering connection 53 and the data connection55 of the circuit 40 implemented on the PCB via connection points 53b and 55b.After the unitary powering connection blade 53a and the data connection blade 55ahave been attached (electrically and physically) to the PCB, the blades 53a and 55acan be physically/electrically separated by removing a frangible portion 57 that canlink the blades 53a and 55a during assembly to the PCB. The powering connectionblade 53a and the data connection blade 55a can each form a separate "male" terminal. Similarly, the ground terminal lead 47 can also be implemented as a "male" 12 terminal at the kill switch terminal 44. In this configuration, the kill switch terminal44 can also include the kill switch that uses three "female" receptacles for receivingthe powering connection blade 53a, the data connection blade 55a, and the groundterminal lead 47.
    Preferably, after the frangible portion 57 has been removed from the terminal44 the outer perimeter or footprint of its two separate connector legs 53a, 55acollectively have an outer perimeter, width, and thickness which is substantially thesame as a conventional spade terminal currently used only as a single engineconnection to a conventional kill switch of a light duty engine. This perrnitsutilization of the same conventional kill switch and at the same location as theconventional stop spade connecter terminal for the normal stopping of the operatingengine function and when this kill switch is removed also perrnits the microprocessorpowering and data transfer fianction to be performed through the interrnediate deviceor interface to an extemal digital computer. This also facilitates the assembly of theterminal 44 to the PCB and routing its electrically conductive traces to both legs 53a,55a. This also facilitates encapsulating the PCB in epoxy or other polymer to protectit and it is both easier and more cost effective to protect both the control module andthe terminal 55. This also perrnits continued use during assembly to the PCB of thelocating hole within the perimeter of the terminal.
    In the first fianction (to perrnit the stoppage of engine operation during normaluse), the female receptacles of the kill switch can receive the powering connectionblade 53a, the data connection blade 55a, and the ground terminal lead 47 such thatthe switch is coupled to the powering connection blade 53a, the data connection blade55a, and the ground terminal lead 47.
    While the kill switch is coupled to the powering connection blade 53a, the data connection blade 55a, and the ground 13 terminal lead 47, the kill switch electrically connects to the powering connection 53,the data connection 55, and pin 3 of the microcontroller 46 via resistor 58 shown inFIG.2. When a user closes the kill switch, the connections 53 and 55 are electricallycoupled with the ground terrninal lead 47 via connection 49 (depicted in FIG. 2 by adotted line) to stop norrnal running of the engine.
    During the second fianction (to perrnit the acquisition of data from themicrocontroller 46), the kill switch can be physically separated or disconnected fromthe kill switch terrninal 44 such that the powering connection blade 53a, the dataconnection blade 55a, and the ground terrninal lead 47 are no longer received by or inelectrical contact with the multipurpose switch. The powering connection blade 53a,the data connection blade 55a, and the ground terrninal lead 47 are then exposed andcan then be used for data gathering, which will be discussed below in more detail.
    Turning to FIG. 3, a block diagram of an interrnediary computing device 300is shown. The interrnediary computing device 300 can be an electrical device that iscoupled to the microprocessor 46 via the powering connection 53, the data connection55, and the ground terrninal lead 47 of the circuit 40 shown in FIG. 2. Along withbeing coupled with the powering connection 53, the data connection 55, and theground terrninal lead 47, the interrnediary computing device 300 can also be coupledto a PC 302. In one implementation, the interrnediary computing device 300 caninclude a plug having three "female" receptacles for receiving "male" terrninals of thepowering connection 53, the data connection 55, and the ground terrninal lead 47. Anexample of this plug is discussed in more detail below with respect to FIG. 4. Themulti-fianction switch (not shown) can be separated from the kill switch terrninal 44 ofFIG. 2 to reveal the male terrninals of the powering connection blade 53a, the data connection blade 55a, and the ground terrninal lead 47 and the plug can be f1tted such 14 that the three female receptacles become physically and/or electrically connected tothe powering connection blade 53a, the data connection blade 55a, and the groundterminal lead 47. The interrnediary computing device 300 can also be coupled to thePC 302 via a port 304. The port 304 will be described with respect to FIG. 3 as auniversal serial bus (USB) port. However, it should be appreciated that other types ofserial ports used with PCs are known to those skilled in the art can be used with thesystem described herein.
    The interrnediary computing device 300 can also include a power supplyconditioning circuit 306, an interrnediary microprocessor 308, a current-limited signaldriver 310, and input signal filtering 312. When the interrnediary computing device300 is coupled to both the circuit 40 (via the powering connection 53, the dataconnection 55, and the ground terminal lead 47) and the PC 302, the device 300 canuse the power supply conditioning circuit 306 to power the microprocessor 46 (shownin FIG. 2). In one implementation, the power supply conditioning circuit 306 cancommunicate voltage from the PC 302 to the microprocessor 46 via the port 304 andpowering connection 53. The power supply conditioning circuit 306 can beconfigured to regulate the voltage received from the PC 302 to an amount accepted bythe microprocessor 46. It is also possible for the power supply conditioning circuit toreceive power from a source extemal to the interrnediary computing device 300, suchas an AC power outlet, and convert that power to a DC voltage usable by themicroprocessor 46. The power supply conditioning circuit 306 can also be coupled tothe current-limited signal driver 310, which can act as a current limiter for data sentfrom the interrnediary computing device 300 to the microprocessor 46 via the data connection 55.
    After the microprocessor 46 has been powered up via the powering connection53 using the power supply Conditioning circuit 306, the interrnediary microprocessor308 of the interrnediary computing device 300 can access computer code for directingthe microprocessor 46 to send data via the data connection 55. The computer codecan be implemented in a variety of computer languages known to those skilled in theart, such as "C++," and stored in an EEPROM accessible by the interrnediarymicroprocessor 308. To send data to or access data from microprocessor 46, theintermediary microprocessor 308 can transmit a command via the current limitedsignal driver 3l0 and the data connection 55 that is readable by the microprocessor46. After the microprocessor 46 receives the command from the interrnediarymicroprocessor 308, the microprocessor 46 acts on the command and sends storeddata to the interrnediary computing device 300 via the data connection 55 or preparesto receive additional data from the device 300 via the connection 55. Theinterrnediary computing device 300 can receive data from the processor 46 and pass itthrough the input signal filtering block 312 to the interrnediary microprocessor 308.The interrnediary microprocessor 308 can then send the received data to the PC 302via the port 304. The system can be designed such that when the poweringconnection 53 and the data connection 55 are electrically connected together, the dataconnection 55 may be unable to communicate data because more current will berequired to power the microprocessor 46 than will be available. This can ensure theseparate use of the powering connection 53 and the data connection during datatransfer. For instance, the current limited signal driver 310 can restrict current suchthat when current flows through both the powering connection 53 and the data connection 55 when they are electrically connected together the microcontroller 46 will not receive enough power to carry out data transfer. In one implementation, the 16 current limited signal driver 310 can limit current to values S 1.0 milliamps (mA).Thus, when the powering connection 53 and/or the data connection 55 are electricallyconnected together, current amounts used to obtain data cannot be obtained.
    Once the PC 302 receives the data, the PC 302 can read the data using asoftware program suitable for reading such data. Much like the software used by theinterrnediary microprocessor 308, the software used by the PC 302 to read the datafrom the microprocessor 46 can be created in a variety of computer languages knownto those skilled in the art, such as "C++.“ While the microcontroller 46 is powered viapowering connection 53, the data connection 55 can bi-directionally communicatedata from pin 3 of the microcontroller 46 through interrnediary computing device 300to an outside source, such as the PC 302. This exchange of data can include obtainingstored engine data from the microcontroller 46 or reprogramming or re-flashing thememory of the microcontroller 46.
    Tuming to FIG. 4, a block diagram depicts one embodiment of a light-dutyengine 400 that can be used with the diagnostic data system described herein. Thelight-duty engine 400 is shown along with the interrnediary computing device 300 andan extemal PC 402 that have been described in more detail above. A kill switch 404is shown located on the cowl or cover 406 of light-duty engine 400. The kill switch404 is an example of the switch described above with respect to FIG. 2 as part of thekill switch terminal 44. As noted above, the kill switch 404 can have a first fi.1nction(to perrnit the stoppage of engine operation during normal use) and a second fi.1nction(to perrnit the acquisition or transmission of data fron1/to the microcontroller 46). Thekill switch 404 can frictionally fit within an opening in the cover 406 of the light-dutyengine 400 during the first fianction and the switch 404 can be physically removed from the cover 406 during the second function. 17 FIG. 4 depicts a switch-removed configuration 404a in which the multi-fianction switch 404 has been physically removed from the cover 406 during thesecond function. Such removal reveals the powering connection blade 53a, the dataconnection blade 55a, and the ground terminal 47 described above with respect toFIG. 2. The powering connection blade 53a, the data connection blade 55a, and theground terminal 47 are shown in the switch-removed configuration 404a from aperspective view, which depicts an elongated blade structure for the poweringconnection blade 53a and the data connection blade 55a whereas the ground terminal47 is shown as a pin or rod-like elongated member. The powering connection blade53a, the data connection blade 55a, and the ground terminal 47 can be located whollywithin the cover 406 and yet remain accessible from outside the cover 406 via theswitch-removed configuration 404a.
    When the switch-removed configuration 404a reveals the powering connectionblade 53a, the data connection blade 55a, and the ground terminal 47, theinterrnediary computing device 300 can be connected to the powering connectionblade 53a, the data connection blade 55a, and the ground terminal 47 via a wire 408that is terrninated with a plug 410. The surface of the plug 4l0 that is fitted to thepowering connection blade 53a, the data connection blade 55a, and the groundterminal 47 on or through the switch-removed configuration 404a is shown in moredetail at 4l0a. The plug surface 4l0a includes individual and separate femalereceptacles for each of the powering connection blade 53a, the data connection blade55a, and the ground terminal 47. These elongated female receptacles are shown onsurface 4l0a in a perspective view as a first female receptacle 4l2 and a secondfemale receptacle 4l4. A third female receptacle 4l6 is also shown in a perspective view on the surface 4l0a as a circular female receptacle for receiving the pin ground 18 terminal 47. Once the plug 410 is mated with the powering connection blade 53a, thedata connection blade 55a, and the ground terminal 47 via the switch-removedconfiguration 404a, data communication can commence between the PC 402 and themicrocontroller 46 (shown in FIG. 2) via a USB cable 418, the interrnediarycomputing device 300, the wire 408, and the plug 410 using the powering connectionblade 53a, the data connection blade 55a, and the ground terminal 47. When datatransfer is complete, the plug 410 can be physically removed and disconnected fromthe powering connection blade 53a, the data connection blade 55a, and the pin groundterminal 47. The kill switch 404 can then be retumed to the cover 406 and frictionallyfit into a position where it carries out its first function.
    Tuming to FIG. 5, an exemplary method 500 for recording engine data isshown. Method 500 will be described with reference to devices described withrespect to FIGS. 1-2. The method 500 begins at step 505 by accessing the memory ofthe microcontroller 46 to obtain previous engine data (if any) and loading that dataonto the random access memory (RAM) of the microcontroller 46. This can betriggered by an engine operator attempting to start a light-duty engine, such as wouldoccur when the engine operator began pulling a starter cord to tum the flywheel 12.Engine data can include any one or more data categories, including but not limited totime of engine operation within one or more ranges of revolutions-per-minute (RPM),number of engine starts, number of engine kills, number of engine stalls, and totalhours/minutes of engine operation, to name a few. The method 500 then proceeds tostep 510 to determine if the engine is running. A number of ways exist to establishthis status. For example, if the microcontroller 46 deterrnines that the engine is operating above 1700 RPM for more than 2 seconds, the method 500 can proceed to step 515. Otherwise, the method 500 repeats step 510. 19 At step 515, it is deterrnined whether an engine revolution of the enginecrankshaft has been completed. This can be established by detecting the electricalpulses that are generated by pole shoes 16, 18, and/or perrnanent magnet 17 whenthey induce a magnetic flux in the nearby stator assembly 14. The microcontroller 46can then detect the presence of these pulses within a certain time period and determinea beginning of the engine revolution and an end of the engine revolution. If themicrocontroller 46 detects the end of the engine revolution, then the method 500proceeds to step 520. Otherwise, the method 500 repeats step 515.
    At step 520, the occurrence of one or more engine revolutions and the time ittakes to occur is recorded. This can be done by the microcontroller 46. In oneexample, this can be carried out by detecting the amount of time that has passed sincethe last engine revolution. Using the time that has passed between successive enginerevolutions can indicate the speed of rotation of the engine crankshaft which can beused to determine the RPM of the engine. In one example, the microcontroller 46 cancalculate the amount of time that has passed between successive engine revolutions.The microcontroller 46 can then access a lookup table stored in the memory of themicrocontroller 46 that includes a number of categories. Each category can include atime range that is associated with an engine RPM range. When the microcontroller 46deterrnines that the time that has passed between successive engine revolutions fallswithin the time or RPM range of a particular category, a value associated with thatcategory is incremented. For instance, if the microcontroller 46 accesses the lookuptable and deterrnines that the amount of time that has passed indicates that the engineis operating at 5200 RPM, the microcontroller 46 increments the value of a category associated with the engine running between 5000-6000 RPM. A plurality of categories can be maintained at the microcontroller 46. For instance, categories can be maintained for a large RPM range, such as between 2,000-11,000 RPM, and thecategories can be delineated by Various increments, such as 500 RPM, 1000 RPM, orboth. The microcontroller 46 can maintain/store data representing the cumulatiVenumber of engine reVolutions occurring, as Well as any other engine data, oVer the lifeof the engine. This data is one example of engine data. As subsequent enginerevolutions are recorded, those engine revolutions are added to previously-recordedengine reVolutions and the number and/or rate of RPM oVer a period of time can becalculated based on this comparison. That is, in one example, RPM can bedeterrnined by the number of revolutions the microcontroller 46 detects during aminute of time. As the engine operates, RPM can be recorded during the time theengine operates and can be stored on the microcontroller 46. The method 500 thenproceeds to step 525.
    At step 525, it is deterrnined if the engine has stopped. In one example, thiscan inVolVe the microcontroller 46 detecting the actiVation of the kill switch terminal44. If it is deterrnined that the engine has stopped Via the kill sWitch 44, the method500 proceeds to step 530. Otherwise, the method 500 then proceeds to step 535.
    At step 530, the number of engine stops is incremented. In one example, thiscan inVolVe the microcontroller 46 accessing a previously stored number of enginestops that Was loaded from the memory of the microcontroller 46 onto the RAM andadding one more to that Value. The microcontroller 46 can maintain/store datarepresenting the cumulative number of engine stops occurring over the life of theengine. When the microcontroller 46 detects an engine stop, the recorded number ofengine stops can be incremented. The method 500 then proceeds to step 545.
    If it has not been deterrnined that the engine stopped at step 525, it is deterrnined if the engine has stalled at step 535. In one example, an engine stall can 21 be deterrnined by the microcontroller 46 When it detects an absence of pulsesgenerated by the pole shoes 16, 18 and/or no magnetic flux in the nearby statorassembly 14 coupled With an absence of kill switch terminal 44 activation. If anengine stall is detected, then the method 500 then proceeds to step 540. Otherwise,the method 500 proceeds to step 515 and continues to record engine data.
    At step 540, the number of engine stalls is incremented. In one example, thiscan involve the microcontroller 46 accessing a previously stored number of enginestalls that Was loaded onto the RAM and adding one more to that value. Themicrocontroller 46 can maintain/store data representing the cumulative number ofengine stalls occurring over the life of the engine. When the microcontroller 46detects an engine stall, the recorded number of engine stalls can be incremented. Themethod 500 then proceeds to step 545.
    At step 545 the previously-stored values of engine data are overwritten Withnewly recorded data. This can take place When the engine has either stopped orstalled. In one example, the microcontroller 46 accesses the data that has been storedon the RAM While the engine is running and Writes it onto its memory, such as flashmemory, carried by the microcontroller 46. This can mean that the engine dataobtained during steps 520, 530, and/or 540 is added to previously-gathered enginedata and recorded for later access. In other Words, the engine data gathered in method500 is cumulative, such that the data obtained during the most recent engine use isadded to previous engine operation. The method 500 then ends.
    It Will of course be understood that the foregoing description is of preferredexemplary embodiments of the invention and that the invention is not limited to the specific embodiments shown. Various changes and modifications Will become 22 apparent to those skilled in the art and all such Variations and niodifications are intended to come Within the spirit and scope of the appended clainis. 23
    权利要求:
    Claims (12)
    [1] 1. A spark ignition engine system for communicating data, the system comprising: a capacitive discharge ignition system (10) using a microcontroller (46) for controlling the spark ignition of a light-duty internal combustion engine (400): a memory device communicated with the microcontroller (46), wherein the microcontroller (46) obtains engine data from the light-duty internal combustion engine (400) and stores the engine data or software using the memory device; and a powering connection (53) and a separate data connection (55) that are electrically connected to different pins (3) of the microcontroller (46), wherein the powering connection supplies power to the microcontroller (46) from an external computer while engine data or software is communicated with the external computer via the data connection.
    [2] 2. The spark ignition system of claim 1, further comprising an intermediary computing device (300) that detachably connects with the powering connection (53) for providing power to the microcontroller (46) and the separate data connection for communicating data between the microcontroller (46) and an external personal computer.
    [3] 3. The spark ignition system of claim 1, wherein the powering connection (53) is electrically connected to a powering connection blade (53a) and the data connection (55) is electrically connected to a separate data connection blade (55a). 1
    [4] 4. The spark ignition system of claim 3, wherein the powering connection blade (53a) and the data connection blade (55a) are initially formed as one piece but the powering connection blade (53a) and the data connection blade (55a) are later separated into separate terminals.
    [5] 5. The spark ignition system of claim 4, wherein the powering connection blade (53a) and the data connection blade (55a) are separated by removing a frangible portion (57).
    [6] 6. The spark ignition system of claim 1, wherein the powering connection and the separate data connection are accessed by removing a kill switch from a cover of the light-duty internal combustion engine (400).
    [7] 7. A spark ignition engine system for communicating data, the system comprising: a capacitive discharge ignition system (10) using a microcontroller (46) for controlling the ignition of a light-duty internal combustion engine (400); a memory device communicated with the microcontroller (46), wherein the microcontroller (46) obtains engine data from the light-duty internal combustion engine (400) and stores the engine data or software using the memory device; a data connection coupled with the microcontroller (46); a separate powering connection (53) coupled with the microcontroller (46) for powering the microcontroller (46) while engine data or software is communicated via the data connection; and 2 an intermediary computing device that is detachably coupled to the data connection (55) and the powering connection (53) while engine data or software is communicated via the data connection (55), wherein the intermediary computing device supplies power to the microcontroller (46) via the separate powering connection (53).
    [8] 8. The spark ignition system of claim 7, wherein the powering connection (53) is electrically connected to a powering connection blade (53a) and the data connection (55) is electrically connected to a separate data connection blade (55a).
    [9] 9. The spark ignition system of claim 8, wherein the powering connection blade (53a) and the data connection blade (55a) are initially formed as one piece but the powering connection blade (53a) and the data connection blade (55a) are later separated into separate terminals.
    [10] 10. The spark ignition system of claim 9, wherein the powering connection blade (53a) and the data connection blade (55a) are separated by removing a frangible portion (57).
    [11] 11. The spark ignition system of claim 7, wherein the powering connection (53) and the separate data connection are accessed by removing a kill switch from a cover of the light-duty internal combustion engine (400). 3
    [12] 12. A spark ignition engine system for communicating data, the system comprising: a capacitive discharge ignition system (10) using a microcontroller (46) for controlling the ignition of a light-duty internal combustion engine (400); a memory device communicated with the microcontroller, wherein the microcontroller obtains engine data from the light-duty internal combustion engine and stores the engine data or software using the memory device; and a kill switch that is removably-carried by a cover of the light-duty internal combustion engine (400), wherein the kill switch is in communication with a data connection (55) electrically linked to the microcontroller (46) and with a separate powering connection electrically linked to the microcontroller (46), and when the kill switch is removed and disconnected from the data connection (55) and the powering connection (53), an intermediary computing device is connected to the data connection (55) for communicating data with the microcontroller (46) and the powering connection (53) for providing power. 4 PC Running Custom C++ Software (USB Connected) c--300 U BI-304 1_ GND +5V 306 I Current Limited Signal Driver Ar--` 24 32 34 2
    类似技术:
    公开号 | 公开日 | 专利标题
    SE1551272A1|2015-10-05|Ignition diagnostics system
    US10626839B2|2020-04-21|Ignition system for light-duty combustion engine
    US20210033036A1|2021-02-04|Engine kill switch and control assembly
    JPWO2014163071A1|2017-02-16|Ignition device for internal combustion engine
    AU2008207652A1|2009-11-26|Battery charging and isolation system for gas engine
    US4984543A|1991-01-15|Oil pressure interlock switch powered by the engine starter
    CN108291487B|2021-08-17|Throttle position sensor actuated by throttle trigger and engine control module
    US8807119B2|2014-08-19|Positive detection of engine position during engine starting
    CN110431302B|2021-10-29|Ignition module with low speed control
    US10544745B2|2020-01-28|Engine self-adjustment system
    EP1985843A2|2008-10-29|Capacitor-discharge ignition system for internal combustion engine
    US7826955B2|2010-11-02|General-purpose internal combustion engine
    US20190017456A1|2019-01-17|Engine operator initiated self-adjustment system
    US20170058810A1|2017-03-02|Control with emitter for small engine applications
    US20210254593A1|2021-08-19|Engine ignition control unit for improved engine starting
    WO2014000047A1|2014-01-03|Ignition system, method, and circuit
    US20110126802A1|2011-06-02|Method and Apparatus for Providing Electronic Ignition of Early Automobile Engines
    WO2018237104A1|2018-12-27|Magneto ignition system and ignition control system
    JP5136743B2|2013-02-06|Non-contact ignition control device for internal combustion engine
    同族专利:
    公开号 | 公开日
    DE112014001435T5|2016-01-14|
    CN105189998B|2018-03-30|
    US10119516B2|2018-11-06|
    WO2014150742A1|2014-09-25|
    US20160003210A1|2016-01-07|
    CN105189998A|2015-12-23|
    SE540520C2|2018-09-25|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US4324215A|1980-04-30|1982-04-13|Eltra Corporation|Engine speed limiting circuit|
    US5769051A|1996-05-29|1998-06-23|Bayron; Harry|Data input interface for power and speed controller|
    SE520096C2|1998-12-10|2003-05-27|Atlas Copco Tools Ab|Power tool system including connectable and disconnectable memory module for storing and transferring data between different devices|
    US6721648B2|1999-11-02|2004-04-13|Autotronic Controls Corporation|Method and apparatus for controlling a motorcycle engine|
    US7198028B2|2001-07-18|2007-04-03|Walbro Engine Management, L.L.C.|Ignition timing control system for light duty combustion engines|
    DE102004020539B3|2004-04-27|2005-07-28|Siemens Ag|Electronic control device for vehicle components has a microcontroller to produce control signal, final stage to activate and deactivate components and monitoring device|
    US7136742B2|2004-09-30|2006-11-14|Walbro Engine Management, L.L.C.|Engine kill-switch control circuit and method of operating the same|
    DE102006038278B4|2006-08-16|2022-02-17|Andreas Stihl Ag & Co. Kg|Portable, hand-held tool with a data connection for diagnostics|
    US7546836B2|2007-01-26|2009-06-16|Walbro Engine Management, L.L.C.|Ignition module for use with a light-duty internal combustion engine|
    US8303337B2|2007-06-06|2012-11-06|Veedims, Llc|Hybrid cable for conveying data and power|
    DE102009057731B4|2009-12-10|2022-02-03|Andreas Stihl Ag & Co. Kg|Method for operating an implement with a diagnostic device|
    CN202194731U|2011-08-03|2012-04-18|湛江德利化油器有限公司|Electric control unit of small engine|
    DE102013016028B4|2012-10-31|2019-07-18|Prüfrex engineering e motion gmbh & co. kg|Ignition method for an internal combustion engine and then working igniter|JP6387552B2|2015-03-27|2018-09-12|ヤンマー株式会社|engine|
    WO2017091537A1|2015-11-24|2017-06-01|Walbro Llc|Throttle trigger actuated throttle position sensor and engine control module|
    DE112017000486T5|2016-01-25|2018-10-31|Walbro Llc|ENGINE EMERGENCY STOP AND CONTROL ARRANGEMENT|
    US10954911B2|2016-10-19|2021-03-23|Walbro Llc|Control and communication module for light-duty combustion engine|
    CN111542469B|2017-08-01|2021-12-14|康明斯有限公司|Control logic circuit for connecting multiple high-side loads to common return pin|
    法律状态:
    优先权:
    申请号 | 申请日 | 专利标题
    US201361790419P| true| 2013-03-15|2013-03-15|
    PCT/US2014/024103|WO2014150742A1|2013-03-15|2014-03-12|Ignition diagnostics system|
    [返回顶部]